functions: Accept null repeat intervals - #605
Merged
Merged
Conversation
Weekly and monthly schedules serialize repeat_interval as null. Allow that response shape so one automation cannot invalidate the full functions list.
Contributor
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/cli@0.1.9-pr.605.7ef69e1Prefer not to change any import paths? Install using npm alias so your code still imports npm i "base44@npm:@base44-preview/cli@0.1.9-pr.605.7ef69e1"Or add it to your {
"dependencies": {
"base44": "npm:@base44-preview/cli@0.1.9-pr.605.7ef69e1"
}
}
Preview published to npm registry — try new features instantly! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Function list responses can include
repeat_interval: nullfor weekly and monthly schedules. We now accept that shape and cover both schedule units in the response schema test.Why?
Before this, one such automation caused the entire functions response to fail with
SCHEMA_INVALID, breaking list, pull, remote logs, and force deploy flows for affected apps.🔗 Origin task in dev3: open in dev3 ·
dev3://task/2ca20129-62e3-4069-ba47-b1816823adac